User equipment and method for controlling transmission of same in a wireless communication system

ABSTRACT

A user equipment and a method for controlling transmission of same in a wireless communication system are provided. The user equipment is configured to implement an access stratum (AS) layer. The method includes receiving, from an upper layer to the AS layer, a first indication and a second indication for a packet, wherein the first indication is configured to indicate whether to perform a packet data control protocol (PDCP) duplication, and the second indication is configured to indicate whether to use a release 15 feature and controlling the AS layer not to perform the PDCP duplication and controlling the AS layer not to use the release 15 feature when the first indication indicates to perform the PDCP duplication and the second indication indicates not to use the release 15 feature.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of International ApplicationNo. PCT/CN2019/076465, entitled “USER EQUIPMENT AND METHOD FORCONTROLLING TRANSMISSION OF SAME IN A WIRELESS COMMUNICATION SYSTEM”filed on Feb. 28, 2019, the contents of which are hereby incorporated byreference in its entirety.

BACKGROUND OF DISCLOSURE 1. Field of Disclosure

The present disclosure relates to a field of communication systems, andmore particularly, to a user equipment and a method for controllingtransmission of same in a wireless communication system.

2. Description of Related Art

Latency and reliability play important roles when setting requirementsin wireless communication systems. A packet data control protocol (PDCP)duplication is configured to increase reliability as well as potentiallydecrease latency.

SUMMARY

An object of the present disclosure is to propose a user equipment and amethod for controlling transmission of same in a wireless communicationsystem.

In a first aspect of the present disclosure, a user equipment forcontrolling transmission in a wireless communication system includes amemory, a transceiver, and a processor coupled to the memory and thetransceiver. The processor is configured to implement an access stratum(AS) layer to: receive, from an upper layer to the AS layer, a firstindication and a second indication for a packet, wherein the firstindication is configured to indicate whether to perform a packet datacontrol protocol (PDCP) duplication, and the second indication isconfigured to indicate whether to use a release 15 feature and controlthe AS layer not to perform the PDCP duplication and control the ASlayer not to use the release 15 feature when the first indicationindicates to perform the PDCP duplication and the second indicationindicates not to use the release 15 feature.

In a second aspect of the present disclosure, a method for controllingtransmission of a user equipment in a wireless communication system isprovided. The user equipment is configured to implement an accessstratum (AS) layer. The method includes receiving, from an upper layerto the AS layer, a first indication and a second indication for apacket, wherein the first indication is configured to indicate whetherto perform a packet data control protocol (PDCP) duplication, and thesecond indication is configured to indicate whether to use a release 15feature and controlling the AS layer not to perform the PDCP duplicationand controlling the AS layer not to use the release 15 feature when thefirst indication indicates to perform the PDCP duplication and thesecond indication indicates not to use the release 15 feature.

In a third aspect of the present disclosure, a non-transitorymachine-readable storage medium has stored thereon instructions that,when executed by a computer, cause the computer to perform the abovemethod.

In a fourth aspect of the present disclosure, a terminal device includesa processor and a memory configured to store a computer program. Theprocessor is configured to execute the computer program stored in thememory to perform the above method.

BRIEF DESCRIPTION OF DRAWINGS

In order to more clearly illustrate the embodiments of the presentdisclosure or related art, the following figures will be described inthe embodiments are briefly introduced. It is obvious that the drawingsare merely some embodiments of the present disclosure, a person havingordinary skill in this field can obtain other figures according to thesefigures without paying the premise.

FIG. 1 is a block diagram of a user equipment for controllingtransmission in a wireless communication system according to anembodiment of the present disclosure.

FIG. 2 is a flowchart illustrating a method for controlling transmissionof a user equipment in a wireless communication system according to anembodiment of the present disclosure.

FIG. 3 is a block diagram of a system for wireless communicationaccording to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments of the present disclosure are described in detail with thetechnical matters, structural features, achieved objects, and effectswith reference to the accompanying drawings as follows. Specifically,the terminologies in the embodiments of the present disclosure aremerely for describing the purpose of the certain embodiment, but not tolimit the disclosure.

FIG. 1 illustrates that, in some embodiments, a user equipment (UE) 10for controlling transmission in a wireless communication systemaccording to an embodiment of the present disclosure are provided. TheUE 10 may include a processor 11, a memory 12, and a transceiver 13. Theprocessor 11 may be configured to implement proposed functions,procedures and/or methods described in this description. Layers of radiointerface protocol may be implemented in the processor 11. The memory 12is operatively coupled with the processor 11 and stores a variety ofinformation to operate the processor 11. The transceiver 13 isoperatively coupled with the processor 11, and the transceiver 13transmits and/or receives a radio signal.

The processor 11 may include an application-specific integrated circuit(ASIC), other chipsets, logic circuit and/or data processing devices.The memory 12 may include a read-only memory (ROM), a random accessmemory (RAM), a flash memory, a memory card, a storage medium and/orother storage devices. The transceiver 13 may include baseband circuitryto process radio frequency signals. When the embodiments are implementedin software, the techniques described herein can be implemented withmodules (e.g., procedures, functions, and so on) that perform thefunctions described herein. The modules can be stored in the memory 12and executed by the processor 11. The memory 12 can be implementedwithin the processor 11 or external to the processor 11, in which thosecan be communicatively coupled to the processor 11 via various means areknown in the art.

The communication between UEs relates to vehicle-to-everything (V2X)communication including vehicle-to-vehicle (V2V), vehicle-to-pedestrian(V2P), and vehicle-to-infrastructure/network (V2I/N) according to asidelink technology developed under 3rd generation partnership project(3GPP) release 14, 15, and beyond. UEs communicate with each otherdirectly via a sidelink interface such as a PC5 interface.

In some embodiments, the processor 11 is configured to implement anaccess stratum (AS) layer to: receive, from an upper layer to the ASlayer, a first indication and a second indication for a packet, whereinthe first indication is configured to indicate whether to perform apacket data control protocol (PDCP) duplication, and the secondindication is configured to indicate whether to use a release 15 featureand control the AS layer not to perform the PDCP duplication and controlthe AS layer not to use the release 15 feature when the first indicationindicates to perform the PDCP duplication and the second indicationindicates not to use the release 15 feature.

In some embodiments, the first indication is a proximity-based services(ProSe) per packet reliability (PPPR) indication. In details, the PPPRindication includes a PPPR having eight values ranging from one toeight. When a value of the PPPR is less than a threshold value, thefirst indication indicates to perform the PDCP duplication.

In some embodiments, the second indication indicating whether to use therelease 15 feature further includes the second indication indicatingwhether to use release 14 non-compatible features. In details, therelease 14 non-compatible features can be used corresponding to usingthe release 15 feature. The release 14 non-compatible features cannot beused corresponding to not to use the release 15 feature.

In some embodiments, the release 14 non-compatible features and therelease 15 feature are associated. In details, the release 14non-compatible features and the release 15 feature both include arelease 15 format including rate matching, transport block size (TBS)scaling, and/or a modulation and coding scheme (MCS) table supporting a64 quadrature amplitude modulation (64QAM).

In some embodiments, when the second indication indicates to use therelease 15 feature, the second indication indicates to use a release 15format including using rate matching, transport block size (TBS)scaling, and/or a modulation and coding scheme (MCS) table supporting a64 quadrature amplitude modulation (64QAM) to transmit a correspondingV2X packet.

In some embodiments, the processor 11 is configured to implement anaccess stratum (AS) layer to: receive, from an upper layer to the ASlayer, a first indication and a second indication for a packet and/orservice, determine a plurality of combinations of the first indicationand the second indication, and control the AS layer to treat onecombination of the first indication and the second indication as anothercombination of the first indication and the second indication.

FIG. 2 illustrates a method 200 for controlling transmission of the UE10 in a wireless communication system according to an embodiment of thepresent disclosure.

In some embodiments, the user equipment 10 is configured to implement anaccess stratum (AS) layer. The method 200 includes: at block 202,receiving, from an upper layer to the AS layer, a first indication and asecond indication for a packet, wherein the first indication isconfigured to indicate whether to perform a packet data control protocol(PDCP) duplication, and the second indication is configured to indicatewhether to use a release 15 feature and controlling the AS layer not toperform the PDCP duplication, and at block 204, controlling the AS layernot to perform the PDCP duplication and controlling the AS layer not touse the release 15 feature when the first indication indicates toperform the PDCP duplication and the second indication indicates not touse the release 15 feature.

In some embodiments, the first indication is a proximity-based services(ProSe) per packet reliability (PPPR) indication. In details, the PPPRindication includes a PPPR having eight values ranging from one toeight. When a value of the PPPR is less than a threshold value, thefirst indication indicates to perform the PDCP duplication.

In some embodiments, the second indication indicating whether to use therelease 15 feature further includes the second indication indicatingwhether to use release 14 non-compatible features. In details, therelease 14 non-compatible features can be used corresponding to usingthe release 15 feature. The release 14 non-compatible features cannot beused corresponding to not to use the release 15 feature.

In some embodiments, the release 14 non-compatible features and therelease 15 feature are associated. In details, the release 14non-compatible features and the release 15 feature both include arelease 15 format including rate matching, transport block size (TBS)scaling, and/or a modulation and coding scheme (MCS) table supporting a64 quadrature amplitude modulation (64QAM).

In some embodiments, the user equipment 10 is configured to implement anaccess stratum (AS) layer. The method includes: receiving, from an upperlayer to an access stratum (AS) layer, a first indication and a secondindication for a packet and/or service, determining a plurality ofcombinations of the first indication and the second indication, andcontrolling the AS layer to treat one combination of the firstindication and the second indication as another combination of the firstindication and the second indication.

In some embodiments, controlling the AS layer to treat the onecombination of the first indication and the second indication as theanother combination of the first indication and the second indicationfurther includes controlling the AS layer to override the onecombination of the first indication and the second indication with theanother combination of the first indication and the second indication.

In some embodiments, the first indication is a proximity-based services(ProSe) per packet reliability (PPPR) indication. The second indicationis a release version indication configured to indicate the AS layer ausage of a release 14 feature or a release 15 feature. In details, theusage of the release 15 feature includes using a release 15 formatincluding using rate matching, transport block size (TBS) scaling,and/or a modulation and coding scheme (MCS) table supporting a 64quadrature amplitude modulation (64QAM) to transmit a corresponding V2Xpacket.

Further, in some embodiments, the one combination of the firstindication and the second indication includes that a specific value(s)of PPPR is/are used and the release 14 feature is used. The anothercombination of the first indication and the second indication includesthe specific value(s) of PPPR is/are not used and the release 14 featureis used.

In release 15 eV2x, 3GPP introduces following factors for the AS layerto decide on transmission mechanism. PPPR is provided by the upper layerand is used to indicate the AS layer on a required reliability (e.g.,90%, 99.9%, 99.99%, and etc.) for a specific packet and/or service.According to the PPPR, the AS layer knows whether to use a specifictransmission mechanism (e.g., PDCP duplication) to improve reliability.A release version indication (the name of it is under discussion) isprovided by the upper layer and is used to indicate the AS layer on theusage of the release 15 feature for a specific packet and/or service.Based on it, the AS layer knows whether to use the release 15 feature.

Therefore, there would be rigorously four combinations for the twofactors (such as PPPR and the release version indication).

Combination 1. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) cannot be used.

Combination 2. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) can be used.

Combination 3. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) cannot be used.

Combination 4. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) can be used.

Where the combination 1 is problematic one, because, on one hand, therelease 15 feature (such as release 14 non-compatible features) cannotbe used, which means that the release 14 transmission mechanism is usedto ensure a reception of legacy release 14 V2X UEs. On another hand,PPPR indicates that PDCP duplication is used, and 3GPP agrees to makeuse of a reserved MAC link control identifier (LCID) values in therelease 14 to support PDCP duplication, which means that PDCPduplication is not fully release 14 compatibles. Therefore, the problemis how to solve the conflict between the two aspects.

In more details, the release 14 LCID usable is defined as follows (in TS36.321).

TABLE 1 Values of LCID for a sidelink shared channel (SL-SCH). IndexLCID values 00000 Reserved 00001-01010 Identity of the logical channel01011-10100 Identity of the logical channel which is used forduplication 10101-11011 Reserved 11100 PC5-S messages that are notprotected 11101 PC5-S messages “Direct Security Mode Command” and“Direct Security Mode Complete” 11110 Other PC5-S messages that areprotected 11111 Padding

For a reserved LCID, a release 14 UE would not recognize the reservedLCID, and thus if a MAC PDU contains a MAC sub-header, which contains areserved and/or invalid LCID, a whole MAC PDU would be discarded, i.e.,according to TS 36.321. When a MAC entity receives a MAC PDU for the MACentity's C-RNTI or semi-persistent scheduling C-RNTI, or by a configureddownlink assignment, or on the SL-SCH, containing reserved or invalidvalues, the MAC entity discards the received PDU.

In addition, PDCP duplication defined in the release 15 is to make useof the reserved LCID values defined in the release 14, as long as aduplicated MAC SDU is contained in a specific MAC PDU, the whole MAC PDUwould be discarded, even if the other MAC SDUs contains valid LCID, andis received by release 14 UEs. In one word, this would cause packetloss.

In one embodiment, when the upper layer provides the two factors (PPPRand release version indication), only three combination would bepossible.

Combination 2. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) can be used.

Combination 3. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) cannot be used.

Combination 4. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) can be used.

The combination 1 would be excluded by the upper layer already.

When the lower layer gets different packets and/or services from theupper layer, the different packets and/or services may be associatedwith the following factor combinations. Packet and/or service 1 isassociated with the combination 2. Packet and/or service 2 is associatedwith the combination 3. Packet and/or service 3 is associated with thecombination 4.

Further, the AS layer would generate separate MAC PDUs, this is just toillustrate that the MAC PDUs for the packets and/or services 1 and 3 andthe packet and/or service 2 are separated, but it is still allowed touse multiple MAC PDUs to serve the packets and/or services 1 and 3, andit is also allowed to use multiple MAC PDUs to serve the packet and/orservice 2. For example, MAC PDU A is configured to serve the packetand/or service 1 and 3. MAC PDU B is configured to serve the packetand/or service 2. Where the MAC PDU A is to be received by a release 15UE only since it is not release 14 compatibles, but MAC PDU B can bereceived by both release 14 UE and release 15 UE since it is release 14compatibles.

In another embodiment, when the upper layer provides the two factors(PPPR and release version indication), still four combination would bepossible.

Combination 1. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) cannot be used.

Combination 2. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) can be used.

Combination 3. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) cannot be used.

Combination 4. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) can be used.

When the lower layer gets different packets and/or services from theupper layer, the different packets and/or services may be associatedwith the following factor combinations.

Packet and/or service 1 is associated with the combination 1. Packetand/or service 2 is associated with the combination 2. Packet and/orservice 3 is associated with the combination 3. Packet and/or service 4is associated with the combination 4.

The AS layer would first override the factor combination of packetand/or service 1, either to factor combination of 2 or 3. In thefollowing, it is assumed that the AS layer overrides the combination 1with the combination 2, but the similar procedure can be applicable tocombination 3 as well. That is, the AS layer overrides the combination 1with the combination 3.

In some embodiments, the AS layer overrides the combination 1 with thecombination 2. Therefore, packet and/or service 1 is associated with thecombination 2. Packet and/or service 2 is associated with thecombination 2. Packet and/or service 3 is associated with thecombination 3. Packet and/or service 4 is associated with thecombination 4.

In some embodiments, the AS layer overrides the combination 1 with thecombination 3. Therefore, packet and/or service 1 is associated with thecombination 3. Packet and/or service 2 is associated with thecombination 2. Packet and/or service 3 is associated with thecombination 3. Packet and/or service 4 is associated with thecombination 4.

The AS layer would generate separate MAC PDUs, this is just toillustrate that the MAC PDUs for packets and/or services 1/2/4 and 3 areseparated, but it is still allowed to use multiple MAC PDUs to servepacket and/or service 1/2/4, and it is also allowed to use multiple MACPDUs to serve packet and/or service 3.

For example, MAC PDU A is configured to serve the packet and/or service1, 2, and 4. MAC PDU B is configured to serve the packet and/or service3. Where the MAC PDU A is to be received by a release 15 UE only sinceit is not release 14 compatibles, but MAC PDU B can be received by bothrelease 14 UE and release 15 UE since it is release 14 compatibles.

In some embodiments, when the upper layer provides the two factors (PPPRand release version indication), still four combination would bepossible.

Combination 1. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) cannot be used.

Combination 2. PPPR indicates that PDCP duplication is needed, and therelease version indication indicates that the release 15 feature (suchas release 14 non-compatible features) can be used.

Combination 3. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) cannot be used.

Combination 4. PPPR indicates that PDCP duplication is not needed, andthe release version indication indicates that the release 15 feature(such as release 14 non-compatible features) can be used.

When the lower layer gets different packets and/or services from theupper layer, the different packets and/or services may be associatedwith the following factor combinations:

Packet and/or service 1 is associated with the combination 1. Packetand/or service 2 is associated with the combination 2. Packet and/orservice 3 is associated with the combination 3. Packet and/or service 4is associated with the combination 4.

For packet and/or service 1, the AS layer still follows the upper layerindication, i.e., keep the factor combination 1 as it is. Whengenerating MAC PDUs, in the packet and/or service 1, PDCP duplication isto be used, e.g., it would generate two duplicated PDCP PDU, i.e., PDCPPDUs I and II. For MAC SDUs generated from the PDCP PDU I, it uses theLCID compatible with release 14, i.e., reserved LCID is not used. ForMAC SDUs generated from PDCP PDU II, it uses the LCID is non-compatiblewith release 14 (such as the release 15 feature), i.e., reserved LCID isused.

The embodiments are not limited to the case the packet and/or service 1is only for a single PDCP PDU, but just use that to illustrate theprocedure. In other words, there can be multiple PDCP PDUs included inthe packet and/or service 1.

The AS layer would generate separate MAC PDUs, this is just toillustrate that the MAC PDUs for the packets and/or services 2 and 4,MAC SDUs generated from the PDCP PDU II of the packets and/or services 1and 3, and MAC SDUs generated from the PDCP PDU I of the packet and/orservice 1 are separated, but it is still allowed to use multiple MACPDUs to serve the packets and/or services 2 and 4, and the MAC SDUsgenerated from the PDCP PDU II of the packet and/or service 1, and it isalso allowed to use multiple MAC PDUs to serve the packet and/or service3 and MAC SDUs generated from the PDCP PDU I of the packet and/orservice.

For example, MAC PDU A is configured to serve the packets and/orservices 2 and 4 and MAC SDUs generated from the PDCP PDU II of thepacket and/or service 1. MAC PDU B for the packet and/or service 3, andMAC SDUs generated from the PDCP PDU I of the packet and/or service 1.Where the MAC PDU A is to be received by a release 15 UE only since itis not release 14 compatibles, but MAC PDU B can be received by bothrelease 14 UE and release 15 UE since it is release 14 compatibles.

In some embodiments, the problem is how to enable release 14 compatibletransmission mechanism and PDCP duplication at the same time. Thesolution can be divided into two types.

Type 1: when the upper layer provides input factors of PPPR and releaseversion indication to the AS layer, the following combination isexcluded.

1. On one hand, PPPR is applied and/or present (or a specific value ofPPPR is applied and/or present), i.e., reliable transmission is requiredfor the packet and/or service.

2. On another hand, release 14 compatible transmission mechanism isrequired, i.e., release 15 rate matching scheme, release 15 MCS/TBStable, 64QAM, or transmit diversity is not used.

Type 2: although the upper provides the input factors of PPPR andrelease version indication to the AS layer in a way that the problematiccombination (as described above), but the AS layer solve that by

1. Either override that one combination with another combinations, i.e.,it is essentially the AS layer to remove the problematic combination.

2. Or still follow the upper layer indicated factor combination, butseparate the two duplicated PDCP PDUs.

For PDCP PDU 1, the embodiment uses legacy release 14 LCID values, anduses release 14 compatible transmission mechanism. For PDCP PDU 2, theembodiment uses release 14 reserved LCID values, and uses release 14non-compatible (such as release 15 feature) transmission mechanism.

FIG. 3 is a block diagram of an example system 700 for wirelesscommunication according to an embodiment of the present disclosure.Embodiments described herein may be implemented into the system usingany suitably configured hardware and/or software. FIG. 3 illustrates thesystem 700 including a radio frequency (RF) circuitry 710, a basebandcircuitry 720, an application circuitry 730, a memory/storage 740, adisplay 750, a camera 760, a sensor 770, and an input/output (I/O)interface 780, coupled with each other at least as illustrated.

The application circuitry 730 may include a circuitry, such as, but notlimited to, one or more single-core or multi-core processors. Theprocessors may include any combinations of general-purpose processorsand dedicated processors, such as graphics processors and applicationprocessors. The processors may be coupled with the memory/storage andconfigured to execute instructions stored in the memory/storage toenable various applications and/or operating systems running on thesystem.

The baseband circuitry 720 may include a circuitry, such as, but notlimited to, one or more single-core or multi-core processors. Theprocessors may include a baseband processor. The baseband circuitry mayhandle various radio control functions that enable communication withone or more radio networks via the RF circuitry. The radio controlfunctions may include, but are not limited to, signal modulation,encoding, decoding, radio frequency shifting, etc. In some embodiments,the baseband circuitry may provide for communication compatible with oneor more radio technologies. For example, in some embodiments, thebaseband circuitry may support communication with an evolved universalterrestrial radio access network (EUTRAN) and/or other wirelessmetropolitan area networks (WMAN), a wireless local area network (WLAN),a wireless personal area network (WPAN). Embodiments in which thebaseband circuitry is configured to support radio communications of morethan one wireless protocol may be referred to as multi-mode basebandcircuitry.

In various embodiments, the baseband circuitry 720 may include circuitryto operate with signals that are not strictly considered as being in abaseband frequency. For example, in some embodiments, baseband circuitrymay include circuitry to operate with signals having an intermediatefrequency, which is between a baseband frequency and a radio frequency.

The RF circuitry 710 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork.

In various embodiments, the RF circuitry 710 may include circuitry tooperate with signals that are not strictly considered as being in aradio frequency. For example, in some embodiments, RF circuitry mayinclude circuitry to operate with signals having an intermediatefrequency, which is between a baseband frequency and a radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, orreceiver circuitry discussed above with respect to the user equipment,eNB, or gNB may be embodied in whole or in part in one or more of the RFcircuitry, the baseband circuitry, and/or the application circuitry. Asused herein, “circuitry” may refer to, be part of, or include anApplication Specific Integrated Circuit (ASIC), an electronic circuit, aprocessor (shared, dedicated, or group), and/or a memory (shared,dedicated, or group) that execute one or more software or firmwareprograms, a combinational logic circuit, and/or other suitable hardwarecomponents that provide the described functionality. In someembodiments, the electronic device circuitry may be implemented in, orfunctions associated with the circuitry may be implemented by, one ormore software or firmware modules.

In some embodiments, some or all of the constituent components of thebaseband circuitry, the application circuitry, and/or the memory/storagemay be implemented together on a system on a chip (SOC).

The memory/storage 740 may be used to load and store data and/orinstructions, for example, for system. The memory/storage for oneembodiment may include any combination of suitable volatile memory, suchas dynamic random access memory (DRAM)), and/or non-volatile memory,such as flash memory.

In various embodiments, the I/O interface 780 may include one or moreuser interfaces designed to enable user interaction with the systemand/or peripheral component interfaces designed to enable peripheralcomponent interaction with the system. User interfaces may include, butare not limited to a physical keyboard or keypad, a touchpad, a speaker,a microphone, etc. Peripheral component interfaces may include, but arenot limited to, a non-volatile memory port, a universal serial bus (USB)port, an audio jack, and a power supply interface.

In various embodiments, the sensor 770 may include one or more sensingdevices to determine environmental conditions and/or locationinformation related to the system. In some embodiments, the sensors mayinclude, but are not limited to, a gyro sensor, an accelerometer, aproximity sensor, an ambient light sensor, and a positioning unit. Thepositioning unit may also be part of, or interact with, the basebandcircuitry and/or RF circuitry to communicate with components of apositioning network, e.g., a global positioning system (GPS) satellite.

In various embodiments, the display 750 may include a display, such as aliquid crystal display and a touch screen display. In variousembodiments, the system 700 may be a mobile computing device such as,but not limited to, a laptop computing device, a tablet computingdevice, a netbook, an ultrabook, a smartphone, etc. In variousembodiments, system may have more or less components, and/or differentarchitectures. Where appropriate, methods described herein may beimplemented as a computer program. The computer program may be stored ona storage medium, such as a non-transitory storage medium.

In the embodiment of the present disclosure, a user equipment and amethod for controlling transmission of same in a wireless communicationsystem to reach low latency and high reliability are provided. Theembodiment of the present disclosure is a combination oftechniques/processes that can be adopted in 3GPP specification to createan end product.

A person having ordinary skill in the art understands that each of theunits, algorithm, and steps described and disclosed in the embodimentsof the present disclosure are realized using electronic hardware orcombinations of software for computers and electronic hardware. Whetherthe functions run in hardware or software depends on the condition ofapplication and design requirement for a technical plan. A person havingordinary skill in the art can use different ways to realize the functionfor each specific application while such realizations should not gobeyond the scope of the present disclosure. It is understood by a personhaving ordinary skill in the art that he/she can refer to the workingprocesses of the system, device, and unit in the above-mentionedembodiment since the working processes of the above-mentioned system,device, and unit are basically the same. For easy description andsimplicity, these working processes will not be detailed.

It is understood that the disclosed system, device, and method in theembodiments of the present disclosure can be realized with other ways.The above-mentioned embodiments are exemplary only. The division of theunits is merely based on logical functions while other divisions existin realization. It is possible that a plurality of units or componentsare combined or integrated in another system. It is also possible thatsome characteristics are omitted or skipped. On the other hand, thedisplayed or discussed mutual coupling, direct coupling, orcommunicative coupling operate through some ports, devices, or unitswhether indirectly or communicatively by ways of electrical, mechanical,or other kinds of forms.

The units as separating components for explanation are or are notphysically separated. The units for display are or are not physicalunits, that is, located in one place or distributed on a plurality ofnetwork units. Some or all of the units are used according to thepurposes of the embodiments. Moreover, each of the functional units ineach of the embodiments can be integrated in one processing unit,physically independent, or integrated in one processing unit with two ormore than two units.

If the software function unit is realized and used and sold as aproduct, it can be stored in a readable storage medium in a computer.Based on this understanding, the technical plan proposed by the presentdisclosure can be essentially or partially realized as the form of asoftware product. Or, one part of the technical plan beneficial to theconventional technology can be realized as the form of a softwareproduct. The software product in the computer is stored in a storagemedium, including a plurality of commands for a computational device(such as a personal computer, a server, or a network device) to run allor some of the steps disclosed by the embodiments of the presentdisclosure. The storage medium includes a USB disk, a mobile hard disk,a read-only memory (ROM), a random access memory (RAM), a floppy disk,or other kinds of media capable of storing program codes.

While the present disclosure has been described in connection with whatis considered the most practical and preferred embodiments, it isunderstood that the present disclosure is not limited to the disclosedembodiments but is intended to cover various arrangements made withoutdeparting from the scope of the broadest interpretation of the appendedclaims.

What is claimed is:
 1. A user equipment for controlling transmission ina wireless communication system, comprising: a memory; a transceiver;and a processor coupled to the memory and the transceiver, wherein theprocessor is configured to implement an access stratum (AS) layer to:receive, from an upper layer to the AS layer, a first indication and asecond indication for a packet, wherein the first indication isconfigured to indicate whether to perform a packet data control protocol(PDCP) duplication, and the second indication is configured to indicatewhether to use features of a first release version; control the AS layernot to perform the PDCP duplication and control the AS layer not to usethe features of the first release version when the first indicationindicates to perform the PDCP duplication and the second indicationindicates not to use the features of the first release version; and whenthe second indication indicates to use the features of the first releaseversion, the second indication indicates to use a format of the firstrelease version comprising using rate matching, transport block size(TBS) scaling, and/or a modulation and coding scheme (MCS) tablesupporting a 64 quadrature amplitude modulation (64QAM) to transmit acorresponding V2X packet.
 2. The user equipment of claim 1, wherein thefirst indication is a proximity-based services (ProSe) per packetreliability (PPPR) indication.
 3. The user equipment of claim 2, whereinthe PPPR indication comprises a PPPR having eight values ranging fromone to eight, when a value of the PPPR is less than a threshold value,the first indication indicates to perform the PDCP duplication.
 4. Theuser equipment of claim 1, wherein the second indication is a releaseversion indication configured to indicate the AS layer a usage of afeatures of a second release version or the features of the firstrelease version.
 5. The user equipment of claim 1, wherein the secondindication indicating whether to use the features of the first releaseversion further comprises the second indication indicating whether touse features that are not compatible with a second release version. 6.The user equipment of claim 5, wherein the features that are notcompatible with a second release version and the features of the firstrelease version are associated.
 7. A method for controlling transmissionof a user equipment in a wireless communication system, wherein the userequipment is configured to implement an access stratum (AS) layer, themethod comprising: receiving, from an upper layer to the AS layer, afirst indication and a second indication for a packet, wherein the firstindication is configured to indicate whether to perform a packet datacontrol protocol (PDCP) duplication, and the second indication isconfigured to indicate whether to use a features of a first releaseversion; controlling the AS layer not to perform the PDCP duplicationand controlling the AS layer not to use the features of the firstrelease version when the first indication indicates to perform the PDCPduplication and the second indication indicates not to use the featuresof the first release version; when the second indication indicates touse the features of the first release version, the second indicationindicates to use a format of the first release version comprising usingrate matching, transport block size (TBS) scaling, and/or a modulationand coding scheme (MCS) table supporting a 64 quadrature amplitudemodulation (64QAM) to transmit a corresponding V2X packet.
 8. The methodof claim 7, wherein the first indication is a proximity-based services(ProSe) per packet reliability (PPPR) indication.
 9. The method of claim8, wherein the PPPR indication comprises a PPPR having eight valuesranging from one to eight, when a value of the PPPR is less than athreshold value, the first indication indicates to perform the PDCPduplication.
 10. The method of claim 7, wherein the second indication isa release version indication configured to indicate the AS layer a usageof a features of a second release version or the features of the firstrelease version.
 11. The method of claim 7, wherein the secondindication indicating whether to use the features of the first releaseversion further comprises the second indication indicating whether touse features that are not compatible with a second release version. 12.The method of claim 11, wherein the features that are not compatiblewith a second release version and the features of the first releaseversion are associated.
 13. A non-transitory machine-readable storagemedium having stored thereon instructions that, when executed by acomputer, cause the computer to perform a method for controllingtransmission of a user equipment in a wireless communication system,wherein the user equipment is configured to implement an access stratum(AS) layer, the method comprising: receiving, from an upper layer to theAS layer, a first indication and a second indication for a packet,wherein the first indication is configured to indicate whether toperform a packet data control protocol (PDCP) duplication, and thesecond indication is configured to indicate whether to use a features ofa first release version; controlling the AS layer not to perform thePDCP duplication and controlling the AS layer not to use the features ofthe first release version when the first indication indicates to performthe PDCP duplication and the second indication indicates not to use thefeatures of the first release version; when the second indicationindicates to use the features of the first release version, the secondindication indicates to use a format of the first release versioncomprising using rate matching, transport block size (TBS) scaling,and/or a modulation and coding scheme (MCS) table supporting a 64quadrature amplitude modulation (64QAM) to transmit a corresponding V2Xpacket.
 14. The non-transitory machine-readable storage medium of claim13, wherein the first indication is a proximity-based services (ProSe)per packet reliability (PPPR) indication.
 15. The non-transitorymachine-readable storage medium of claim 14, wherein the PPPR indicationcomprises a PPPR having eight values ranging from one to eight, when avalue of the PPPR is less than a threshold value, the first indicationindicates to perform the PDCP duplication.
 16. The non-transitorymachine-readable storage medium of claim 13, wherein the secondindication is a release version indication configured to indicate the ASlayer a usage of a features of a second release version or the featuresof the first release version.
 17. The non-transitory machine-readablestorage medium of claim 13, wherein the second indication indicatingwhether to use the features of the first release version furthercomprises the second indication indicating whether to use features thatare not compatible with a second release version.
 18. The non-transitorymachine-readable storage medium of claim 17, wherein the features thatare not compatible with a second release version and the features of thefirst release version are associated.